Conditions, Condition

Well Test > Configuring CygNet Well Test > Configuring Well Test Using XML > Elements and Attributes > Conditions, Condition

Conditions, Condition

The Monitor action type must specify one or more monitor definition blocks in the configuration XML. Each monitor block is contained within the <Monitors> element. Each <Monitors> element contains one or more <Monitor> blocks, each containing one or more <Conditions> and <Actions>. And each of these elements may contain one or more <Condition> and/or <Action> to perform.

To learn about how these elements relate to other elements in a well test configuration XML structure, see Well Test Hierarchy.

Example

</Conditions>

</Actions>

</Monitor>

</Conditions>

</Actions>

</Monitor>

</Monitors>

</Action>

Conditions

The <Conditions> element has one type of child element, <Condition>, and has no attributes.

Conditions Properties

The <Conditions> element has the following properties:

Property	Description
Case Sensitive	Yes
Required	Yes
Number of Instances Allowed	Unlimited
Parent Element	<Monitor>
Child Elements	<Condition>
Attributes	None

Condition

A Condition is used to compare two values or to monitor for a change on point value, and if true, perform an action.

Condition Properties

The <Condition> element has the following properties:

Property	Description
Case Sensitive	Yes
Required	Yes
Number of Instances Allowed	Unlimited
Parent Element	<Conditions>
Child Elements	None
Attributes	operator value1 value1Type value1RelativeFacilityLink value2 value2Type value2RelativeFacilityLink

Condition Attributes

The <Condition> element has the following attributes:

Attribute	Required	Description
operator	No	Specifies the operation used for the comparison. Acceptable values include: Equal — = (operator="=") Greater than — > (operator=">") Greater than or equal — >= (operator=">=") Less than — < (operator="<") Less than or equal — <= (operator="<=") Not equal — <> (operator="<>") Changed — CHANGED (operator="CHANGED") The CHANGED operation will only check the first set of values (value1, value1Type, and value1RelativeFacilityLink) to determine which point to monitor for change. The second set of values (value2, value2Type, and value2RelativeFacilityLink) are ignored.
value1	Yes	Specifies the first value to use when comparing the point value in the expression: if the Value 1 Type (value1Type) is Self, then the value of this property will be used in the comparison. if the Value 1 Type (value1Type) is UDC, then the value from the point will be used in the comparison. Click the browse button to open the Select UDC dialog box and select an appropriate UDC.
value1Type	Yes	Specifies the first value Type (value1Type) property. Options include Self or UDC.
value1RelativeFacilityLink	No	Specifies the first relative facility tag to use for the action. Note: The facility tag used as the starting point for the relative resolution depends on where this action type is configured. If the action is defined at a position level, then the base facility tag will be the well facility. If defined at the header level, the base facility will be the header facility.
value2	Yes	Specifies the second value to use when comparing the point value in the expression: if the Value 2 Type (value2Type) is Self, then the value of this property will be used in the comparison. if the Value 2 Type (value2Type) is UDC, then the value from the point will be used in the comparison. Click the browse button to open the Select UDC dialog box and select an appropriate UDC.
value2Type	Yes	Specifies the second value Type (value2Type) property. Options include Self or UDC.
value2RelativeFacilityLink	No	Specifies the second relative facility tag to use for the action. Note: The facility tag used as the starting point for the relative resolution depends on where this action type is configured. If the action is defined at a position level, then the base facility tag will be the well facility. If defined at the header level, the base facility will be the header facility.